Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP part of #161: Exploration player base 2 contentcard #125

Closed
wants to merge 27 commits into from

Conversation

veena14cs
Copy link
Contributor

@veena14cs veena14cs commented Sep 17, 2019

Explanation

This PR includes rich-text handling in contentcard. It fetches contents from exploration API and extracts html contents from states

Issues

  • The PR has issues related to databinding in adapter class.

@veena14cs
Copy link
Contributor Author

@BenHenning @rt4914 This PR is in progress I have issues related to databinding in adapter class. I have created custom adapter to support different viewtypes. This PR is to get clarity on whether the approach of fetching data is correct also need suggestions on it. PTAL

@rt4914
Copy link
Contributor

rt4914 commented Sep 18, 2019

@veena14cs can you merge your branch with latest develop before I have a look at your code.

@veena14cs
Copy link
Contributor Author

@veena14cs can you merge your branch with latest develop before I have a look at your code.

Yeah, okay

@BenHenning BenHenning changed the title WIP part of #42: Exploration player base 2 contentcard WIP part of #161: Exploration player base 2 contentcard Sep 20, 2019
Copy link
Member

@BenHenning BenHenning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @veena14cs! Generally, this approach looks good to me. I left a lot of comments, but quite a few are style based. Please do make sure though that all unused code is removed.

Could you also add tests for the new content card list fragment? And please let me know if you run into any issues--I've been having difficulties testing #172 in Robolectric and have been stuck on this for a couple of days.

.idea/codeStyles/Project.xml Show resolved Hide resolved
app/build.gradle Outdated Show resolved Hide resolved
app/src/main/AndroidManifest.xml Outdated Show resolved Hide resolved
@rt4914
Copy link
Contributor

rt4914 commented Sep 25, 2019

@veena14cs can you please merge this with latest develop branch to solve the conflicts. Also, this will make less files to review.

@rt4914
Copy link
Contributor

rt4914 commented Sep 25, 2019

@veena14cs also, remove FakeDataProvide if you are not using that file, because it has been removed from the develop.

Copy link
Member

@BenHenning BenHenning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @veena14cs. I left some comments on the UrlImageParser, but at this point I think this PR is getting too large & doing too many things. Can we split up #161 such that:

  1. We're introducing the structure for exploration player & state (which is also fixing parts of UI Structure: StateCardFragment [Blocked: #122, #150, #161, #162] #163 and UI Structure: ExplorationPlayerFragment/Activity [Blocked: #163] #165)
  2. We're adding support for downloading and playing images
  3. We hook into ExplorationDataController & ExplorationProgressController to wrap up UI Structure: ContentCardView #161, UI Structure: StateCardFragment [Blocked: #122, #150, #161, #162] #163, and UI Structure: ExplorationPlayerFragment/Activity [Blocked: #163] #165?

If it doesn't slow things down, I suggest going farther and keeping the exploration/state/content card stuff all separate to have much smaller PRs.

app/build.gradle Show resolved Hide resolved
RecyclerView.Adapter<RecyclerView.ViewHolder>() {

private val VIEW_TYPE_CONTENT = 1
private val VIEW_TYPE_RIGHT_INTERACTION = 2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't use positional language like 'left/right' since they may be reversed in RTL layouts.

Beyond that, I'm not sure I understand the directionality here. Per the mocks the interaction appears below the content area.

<layout
xmlns:android="http://schemas.android.com/apk/res/android">

<androidx.constraintlayout.widget.ConstraintLayout
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this resolved? I don't see StateFragment being added anywhere.

<layout
xmlns:android="http://schemas.android.com/apk/res/android">

<androidx.constraintlayout.widget.ConstraintLayout
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, will those be added in this PR?

@BenHenning BenHenning assigned veena14cs and unassigned BenHenning Sep 26, 2019
@rt4914 rt4914 removed their assignment Sep 26, 2019
@veena14cs
Copy link
Contributor Author

Duplicate PR of this is created here #189

@veena14cs veena14cs closed this Sep 26, 2019
@veena14cs veena14cs deleted the exploration-player-2-contentcard branch September 26, 2019 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants